Using derived credentials for enrollment with enterprise mobile device management services

ABSTRACT

Methods, systems, and computer-readable media for using derived credentials to enroll a mobile computing device with an enterprise mobile device management system are described herein. In various embodiments, a mobile computing device, responsive to a command to enroll with an enterprise mobile device management server, may launch an enrollment application; send an enrollment request message to the enterprise mobile device management server; switch to a certificate management system application on the mobile computing device; request one or more derived credentials from a certificate management system server; store the one or more derived credentials in a shared vault on the mobile computing device; switch to the enrollment application; retrieve a derived credential of the one or more derived credentials stored in the shared vault; and, provide the derived credential to the enterprise mobile device management server to enroll the mobile computing device with at least one mobile device management service.

FIELD

Aspects described herein generally relate to computers, networking,hardware, and software, cryptography, and security measures in placetherein. More specifically, one or more aspects of the disclosure relateto enterprise mobile device management services, and in particular,relate to using derived credentials for enrollment with enterprisemobile device management services.

BACKGROUND

Enterprises (e.g., corporations, partnerships, governments, academicinstitutions, other organizations, etc.) face continuously increasingrisks of malicious attacks waged against their computer networks andassets. Some enterprises have mitigated the risks of unauthorized accessto their enterprise resources by implementing strong password policiesacross their organizations. The password policies typically forcedenterprise users to create and maintain a myriad of passwords to accessenterprise resources and to regularly change those passwords. However,these password policies have not been without their share of problems.Most enterprise users ended up creating passwords that were easy forthem to remember but were vulnerable to brute force, dictionary, orsocial engineering attacks. Additionally, users tended to forget ormisplace these passwords, leading to issues when attempting to accessenterprise resources.

In order to address some of the issues with password policies, someenterprises have augmented their network and computer securityprocedures to include deployment and maintenance of Personal IdentityVerification (PIV) cards or Common Access Card (CAC) cards. Theadvantages to the enterprise of these cards are at least two-fold.First, the cards are designed to provide two-factor authentication:physical possession of the card and a personal identification number(PIN) known only to the owner of the card. Second, the cards allow anenterprise to generate and assign derived credentials to an enterpriseuser. The term “derived credentials” may refer to cryptographiccredentials that may be derived from those in a PIV or CAC card and maybe stored in a computing device rather than on the card. Through the useof these cards, the enterprise, and not the enterprise user, can controlthe derived credentials that provide access to resources and thelifecycle and/or lifetime of the derived credentials. An enterprise cancreate, assign, change, deprecate, or revoke derived credentials as theenterprise determines necessary to protect their enterprise resources.Stated differently, an enterprise user might not need to know thepasswords needed to access enterprise resources; rather, the enterpriseuser might only need to insert their PIV or CAC card into a card readerand enter their PIN.

With the emergence of a newer generation of computing devices and inparticular with mobile computing devices, the use of PIV and CAC cardshas proved challenging. PIV and CAC cards are geared towards traditionalcomputing devices (e.g., desktop and laptop computers) with which thecard readers can be easily integrated. Mobile devices lack theintegrated smart card readers found in laptop and desktop computers andrequire separate card readers attached to devices to provideauthentication services from the device. Typically, enterprise PIV orCAC card users must authenticate and present their card every instancein which they require a new derived credential. Accordingly, the userexperience of generating derived credentials with a PIV or CAC card on amobile computing device results in negating most of the portability andmobility advantages that the mobile computing devices provide.

The magnitude and complexity of the situation is further increased bythe current trend towards BYOD—bring your own device. BYOD environmentsallow enterprise users to provide their own devices, such as mobilephones, smartphones, tablets, laptops, personal computers, or otherelectronic devices, for work purposes in addition to the computerresources provided by the enterprise. However, BYOD scenarios poseinherent security risks to the enterprise because the enterprisetypically lacks uniform and full control over each employee-provideddevice and because many enterprise users may resist integrating cardreaders to their personal mobile computing devices. In a BYOD world,enterprise mobility management (EMM) solutions are emerging as a popularway to assist in the management and control of remote access toenterprise resources from personal devices. EMM solutions havetraditionally taken the approach of managing mobile computing devicesthrough what are known as mobile device management (MDM) services andmobile application management (MAM) services. Mobile device managementpolicies control mobile computing devices using access control andmonitoring technologies. Mobile application management policies deliverenterprise software to mobile computing devices and administer thatsoftware. These policies support the incorporation of various securityfeatures, including geo-fencing features, remote wipe features,application isolation features, and data vault encryption features.While these EMM solutions increase the security of using personaldevices to access enterprise resources, these solutions are also boundto only increase the number of credentials required to access theenterprise resources. Typically, enterprise users must know and entertheir usernames and network or directory services password or they mustprovide a one-time password (OTP) generated by the EMM server.Furthermore, some EMM solutions may rely on the credentials stored on aPIV or CAC card for identification and authentication, which results inthe enterprise user having to provide their PIV or CAC card every timethey wish to access enterprise resources.

SUMMARY

The following presents a simplified summary of various aspects describedherein. This summary is not an extensive overview, and is not intendedto identify key or critical elements or to delineate the scope of theclaims. The following summary merely presents some concepts in asimplified form as an introductory prelude to the more detaileddescription provided below.

To overcome limitations in the prior art described above, and toovercome other limitations that will be apparent upon reading andunderstanding the present specification, aspects described herein relateto systems, methods, and techniques for using derived credentials forenrollment of mobile computing devices with enterprise mobile devicemanagement services. Advantageously, the systems, methods, andtechniques described herein allow for enrollment of a mobile computingdevice and access of enterprise resources from the enrolled mobilecomputing device without the need for the enterprise user to know orenter their network or directory service password and without the needfor the PIV or CAC card to be physically connected to the mobilecomputing device during enrollment or subsequent access of enterpriseresources.

In accordance with one or more embodiments, a method may comprisereceiving, by a mobile computing device, a command to enroll with anenterprise mobile device management server; in response to receiving thecommand to enroll with the enterprise mobile device management server,launching, by the mobile computing device, an enrollment application;sending, by the mobile computing device, using the enrollmentapplication, an enrollment request message to the enterprise mobiledevice management server; switching, by the mobile computing device,from the enrollment application to a certificate management systemapplication on the mobile computing device; requesting, by the mobilecomputing device, using the certificate management system application,one or more derived credentials from a certificate management systemserver; storing, by the mobile computing device, using the certificatemanagement system application, the one or more derived credentials in ashared vault on the mobile computing device; switching, by the mobilecomputing device, from the certificate management system application tothe enrollment application; retrieving, by the mobile computing device,using the enrollment application, a derived credential of the one ormore derived credentials stored in the shared vault on the mobilecomputing device; and, providing, by the mobile computing device, usingthe enrollment application, the derived credential of the one or morederived credentials retrieved using the enrollment application to theenterprise mobile device management server to enroll the mobilecomputing device with at least one mobile device management serviceprovided by the enterprise mobile device management server.

In some embodiments, the method may further comprise prompting, by themobile computing device, using the enrollment application, a user of themobile computing device, for an address of the enterprise mobile devicemanagement server.

In other embodiments, the method may further comprise requesting, by themobile computing device, using the enrollment application, configurationinformation for the enterprise mobile device management server from anautomatic discovery service; and after requesting the configurationinformation for the enterprise mobile device management server from theautomatic discovery service, receiving, by the mobile computing device,a message comprising the configuration information for the enterprisemobile device management server from the automatic discovery service.The enrollment request message sent to the enterprise mobile devicemanagement server may comprise the configuration information for theenterprise mobile device management server received from the automaticdiscovery service.

Alternatively, in yet other embodiments, the method may further comprisereceiving, by the mobile computing device, using the enrollmentapplication, a password from the user of the mobile computing device;generating, by the mobile computing device, using the enrollmentapplication, a password validation value based on the password receivedfrom the user of the mobile computing device; storing, by the mobilecomputing device, using the enrollment application, the passwordvalidation value in the shared vault on the mobile computing device;providing, by the mobile computing device, using the enrollmentapplication, the password received from the user of the mobile computingdevice to the certificate management system application; and,validating, by the mobile computing device, using the certificatemanagement system application, the provided password to the certificatemanagement system application based on the password validation valuestored in the shared vault on the mobile computing device. The methodmay further comprise receiving, by the mobile computing device,responsive to the enrollment request message, a message from theenterprise mobile device management server comprising passwordcomplexity validation rules; and, validating, by the mobile computingdevice, the password using the password complexity validation rules. Thepassword validation value may be generated by generating a hash of thepassword, and encrypting the hash of the password. The method mayfurther comprise encrypting, by the mobile computing device, using thecertificate management system application, the one or more derivedcredentials based on the password received from the user of the mobilecomputing device and provided to the certificate management systemapplication, prior to storing the one or more derived credentials in theshared vault on the mobile computing device. The method may furthercomprise encrypting, by the mobile computing device, using thecertificate management system application, the one or more derivedcredentials using a private/public key pair, prior to storing the one ormore derived credentials in the shared vault on the mobile computingdevice.

In some instances, prior to switching to the certificate managementsystem application on the mobile computing device, the method mayfurther comprise receiving, by the mobile computing device, responsiveto the enrollment request message, a message from the enterprise mobiledevice management server identifying the certificate management systemapplication on the mobile computing device; and, determining, by themobile computing device, to switch to the certificate management systemapplication on the mobile computing device based on the message receivedfrom the enterprise mobile device management server identifying thecertificate management system application on the mobile computingdevice.

In other instances, the method may further comprise storing, by themobile computing device, using the certificate management systemapplication, at least one derived credential of the one or more derivedcredentials after the enrollment process is completed.

In yet other instances, the enrollment application and the certificatemanagement system application may be digitally signed with an identicaldevelopment signing certificate.

In some embodiments, the method may further comprise retrieving, by themobile computing device, using one or more applications on the mobilecomputing device that are digitally signed with the same developmentsigning certificate as the enrollment application and the certificatemanagement system application, at least one derived credential of theone or more derived credentials from the shared vault; and using, by themobile computing device the at least one derived credential of the oneor more derived credentials retrieved from the shared vault to providefunctionality in the one or more applications on the mobile computingdevice or to access enterprise resources with the one or moreapplications on the mobile computing device.

In some embodiments, the method may further comprise retrieving, by themobile computing device, using the enrollment application, a firstderived credential and a second derived credential from the sharedvault; providing, by the mobile computing device, using the enrollmentapplication, the first derived credential to the enterprise mobiledevice management server to complete mobile device managementenrollment; and, providing, by the mobile computing device, using theenrollment application, the second derived credential to the enterprisemobile device management server to complete mobile applicationmanagement enrollment.

In some embodiments, the mobile computing device may be provisioned bythe enterprise mobile device management server with policies andapplications after the enrollment process is completed.

In other embodiments, prior to requesting the one or more derivedcredentials from the certificate management system server, the methodmay further comprise: authenticating, by the mobile computing device,using the certificate management system application, with thecertificate management system server using the certificate managementsystem application.

In some embodiments, the user of the mobile computing device may beprompted to provide data for identification and authentication purposesfor authenticating with the certificate management system server.

In some embodiments, switching to the certificate management systemapplication on the mobile computing device may comprise: launching theapplication store on the mobile computing device; and, prompting theuser of the mobile computing device to install the certificatemanagement system application, if or when the certificate managementsystem application is not installed on the mobile computing device.

Systems and non-transitory computer readable media may be configured toprovide and/or support various aspects described herein. These andadditional aspects will be appreciated with the benefit of thedisclosures discussed in further detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of aspects described herein and theadvantages thereof may be acquired by referring to the followingdescription in consideration of the accompanying drawings, in which likereference numbers indicate like features, and wherein:

FIG. 1 depicts an illustrative computer system architecture that may beused in accordance with one or more illustrative aspects describedherein.

FIG. 2 depicts an illustrative remote-access system architecture thatmay be used in accordance with one or more illustrative aspectsdescribed herein.

FIG. 3 depicts an illustrative virtualized (hypervisor) systemarchitecture that may be used in accordance with one or moreillustrative aspects described herein.

FIG. 4 depicts an illustrative cloud-based system architecture that maybe used in accordance with one or more illustrative aspects describedherein.

FIG. 5 depicts an illustrative enterprise mobility management system.

FIG. 6 depicts another illustrative enterprise mobility managementsystem.

FIG. 7 depicts an illustrative system architecture in which a mobilecomputing device may enroll with an enterprise mobile device managementserver, according to one or more illustrative aspects described herein.

FIGS. 8A-8C depict an example event sequence for providing a method toenroll a mobile computing device with an enterprise mobile devicemanagement service using derived credentials in accordance with one ormore illustrative aspects described herein.

FIG. 9 depicts an illustrative system architecture in which an enrolledmobile computing device may use derived credentials in order to accessenterprise resources, according to one or more illustrative aspectsdescribed herein.

FIG. 10 depicts an example event sequence for providing a method for acontainerized application to provide derived credentials to anenterprise server in accordance with one or more illustrative aspectsdescribed herein.

FIG. 11 depicts an example method of using derived credentials forenrollment with enterprise mobile device management services accordingto one or more illustrative aspects described herein.

DETAILED DESCRIPTION

In the following description of the various embodiments, reference ismade to the accompanying drawings identified above and which form a parthereof, and in which is shown by way of illustration various embodimentsin which aspects described herein may be practiced. It is to beunderstood that other embodiments may be utilized and structural andfunctional modifications may be made without departing from the scopedescribed herein. Various aspects are capable of other embodiments andof being practiced or being carried out in various different ways.

As a general introduction to the subject matter described in more detailbelow, aspects described herein are directed towards systems, methods,and techniques for using derived credentials for enrollment of mobilecomputing devices with enterprise mobile device management services.Aspects described herein may be used when an employee of an enterprisemay need to enroll their mobile computing device with the enterprisemobile device management services using derived credentials. Otheraspects described herein may be used when an enterprise user may usederived credentials to access enterprise resources from the user'senrolled mobile computing device.

Before discussing these concepts in greater detail, several examples ofcomputing architecture and systems that may be used in implementingand/or otherwise providing various aspects of the disclosure will firstbe discussed with respect to FIGS. 1-6.

It is to be understood that the phraseology and terminology used hereinare for the purpose of description and should not be regarded aslimiting. Rather, the phrases and terms used herein are to be giventheir broadest interpretation and meaning. The use of “including” and“comprising” and variations thereof is meant to encompass the itemslisted thereafter and equivalents thereof as well as additional itemsand equivalents thereof. The use of the terms “mounted,” “connected,”“coupled,” “positioned,” “engaged” and similar terms, is meant toinclude both direct and indirect mounting, connecting, coupling,positioning and engaging.

Computing Architecture

Computer software, hardware, and networks may be utilized in a varietyof different system environments, including standalone, networked,remote-access (aka, remote desktop), virtualized, and/or cloud-basedenvironments, among others. FIG. 1 illustrates one example of a systemarchitecture and data processing device that may be used to implementone or more illustrative aspects described herein in a standalone and/ornetworked environment. Various network nodes 103, 105, 107, and 109 maybe interconnected via a wide area network (WAN) 101, such as theInternet. Other networks may also or alternatively be used, includingprivate intranets, corporate networks, local area networks (LAN),metropolitan area networks (MAN), wireless networks, personal networks(PAN), and the like. Network 101 is for illustration purposes and may bereplaced with fewer or additional computer networks. A local areanetwork may have one or more of any known LAN topology and may use oneor more of a variety of different protocols, such as Ethernet. Devices103, 105, 107, 109 and other devices (not shown) may be connected to oneor more of the networks via twisted pair wires, coaxial cable, fiberoptics, radio waves or other communication media.

The term “network” as used herein and depicted in the drawings refersnot only to systems in which remote storage devices are coupled togethervia one or more communication paths, but also to stand-alone devicesthat may be coupled, from time to time, to such systems that havestorage capability. Consequently, the term “network” includes not only a“physical network” but also a “content network,” which is comprised ofthe data—attributable to a single entity—which resides across allphysical networks.

The components may include data server 103, web server 105, and clientcomputers 107, 109. Data server 103 provides overall access, control andadministration of databases and control software for performing one ormore illustrative aspects describe herein. Data server 103 may beconnected to web server 105 through which users interact with and obtaindata as requested. Alternatively, data server 103 may act as a webserver itself and be directly connected to the Internet. Data server 103may be connected to web server 105 through the network 101 (e.g., theInternet), via direct or indirect connection, or via some other network.Users may interact with the data server 103 using remote computers 107,109, e.g., using a web browser to connect to the data server 103 via oneor more externally exposed web sites hosted by web server 105. Clientcomputers 107, 109 may be used in concert with data server 103 to accessdata stored therein, or may be used for other purposes. For example,from client device 107 a user may access web server 105 using anInternet browser, as is known in the art, or by executing a softwareapplication that communicates with web server 105 and/or data server 103over a computer network (such as the Internet).

Servers and applications may be combined on the same physical machines,and retain separate virtual or logical addresses, or may reside onseparate physical machines. FIG. 1 illustrates just one example of anetwork architecture that may be used, and those of skill in the artwill appreciate that the specific network architecture and dataprocessing devices used may vary, and are secondary to the functionalitythat they provide, as further described herein. For example, servicesprovided by web server 105 and data server 103 may be combined on asingle server.

Each component 103, 105, 107, 109 may be any type of known computer,server, or data processing device. Data server 103, e.g., may include aprocessor 111 controlling overall operation of the data server 103. Dataserver 103 may further include random access memory (RAM) 113, read onlymemory (ROM) 115, network interface 117, input/output interfaces 119(e.g., keyboard, mouse, display, printer, etc.), and memory 121.Input/output (I/O) 119 may include a variety of interface units anddrives for reading, writing, displaying, and/or printing data or files.Memory 121 may further store operating system software 123 forcontrolling overall operation of the data processing device 103, controllogic 125 for instructing data server 103 to perform aspects describedherein, and other application software 127 providing secondary, support,and/or other functionality which may or might not be used in conjunctionwith aspects described herein. The control logic may also be referred toherein as the data server software 125. Functionality of the data serversoftware may refer to operations or decisions made automatically basedon rules coded into the control logic, made manually by a user providinginput into the system, and/or a combination of automatic processingbased on user input (e.g., queries, data updates, etc.).

Memory 121 may also store data used in performance of one or moreaspects described herein, including a first database 129 and a seconddatabase 131. In some embodiments, the first database may include thesecond database (e.g., as a separate table, report, etc.). That is, theinformation can be stored in a single database, or separated intodifferent logical, virtual, or physical databases, depending on systemdesign. Devices 105, 107, 109 may have similar or different architectureas described with respect to device 103. Those of skill in the art willappreciate that the functionality of data processing device 103 (ordevice 105, 107, 109) as described herein may be spread across multipledata processing devices, for example, to distribute processing loadacross multiple computers, to segregate transactions based on geographiclocation, user access level, quality of service (QoS), etc.

One or more aspects may be embodied in computer-usable or readable dataand/or computer-executable instructions, such as in one or more programmodules, executed by one or more computers or other devices as describedherein. Generally, program modules include routines, programs, objects,components, data structures, etc. that perform particular tasks orimplement particular abstract data types when executed by a processor ina computer or other device. The modules may be written in a source codeprogramming language that is subsequently compiled for execution, or maybe written in a scripting language such as (but not limited to)HyperText Markup Language (HTML) or Extensible Markup Language (XML).The computer executable instructions may be stored on a computerreadable medium such as a nonvolatile storage device. Any suitablecomputer readable storage media may be utilized, including hard disks,CD-ROMs, optical storage devices, magnetic storage devices, and/or anycombination thereof. In addition, various transmission (non-storage)media representing data or events as described herein may be transferredbetween a source and a destination in the form of electromagnetic wavestraveling through signal-conducting media such as metal wires, opticalfibers, and/or wireless transmission media (e.g., air and/or space).Various aspects described herein may be embodied as a method, a dataprocessing system, or a computer program product. Therefore, variousfunctionalities may be embodied in whole or in part in software,firmware and/or hardware or hardware equivalents such as integratedcircuits, field programmable gate arrays (FPGA), and the like.Particular data structures may be used to more effectively implement oneor more aspects described herein, and such data structures arecontemplated within the scope of computer executable instructions andcomputer-usable data described herein.

With further reference to FIG. 2, one or more aspects described hereinmay be implemented in a remote-access environment. FIG. 2 depicts anexample system architecture including a generic computing device 201 inan illustrative computing environment 200 that may be used according toone or more illustrative aspects described herein. Generic computingdevice 201 may be used as a server 206 a in a single-server ormulti-server desktop virtualization system (e.g., a remote access orcloud system) configured to provide virtual machines for client accessdevices. The generic computing device 201 may have a processor 203 forcontrolling overall operation of the server and its associatedcomponents, including RAM 205, ROM 207, I/O module 209, and memory 215.

I/O module 209 may include a mouse, keypad, touch screen, scanner,optical reader, and/or stylus (or other input device(s)) through which auser of generic computing device 201 may provide input, and may alsoinclude one or more of a speaker for providing audio output and a videodisplay device for providing textual, audiovisual, and/or graphicaloutput. Software may be stored within memory 215 and/or other storage toprovide instructions to processor 203 for configuring generic computingdevice 201 into a special purpose computing device in order to performvarious functions as described herein. For example, memory 215 may storesoftware used by the computing device 201, such as an operating system217, application programs 219, and an associated database 221.

Computing device 201 may operate in a networked environment supportingconnections to one or more remote computers, such as terminals 240 (alsoreferred to as client devices). The terminals 240 may be personalcomputers, mobile devices, laptop computers, tablets, or servers thatinclude many or all of the elements described above with respect to thegeneric computing device 103 or 201. The network connections depicted inFIG. 2 include a local area network (LAN) 225 and a wide area network(WAN) 229, but may also include other networks. When used in a LANnetworking environment, computing device 201 may be connected to the LAN225 through a network interface or adapter 223. When used in a WANnetworking environment, computing device 201 may include a modem 227 orother wide area network interface for establishing communications overthe WAN 229, such as computer network 230 (e.g., the Internet). It willbe appreciated that the network connections shown are illustrative andother means of establishing a communications link between the computersmay be used. Computing device 201 and/or terminals 240 may also bemobile terminals (e.g., mobile phones, smartphones, personal digitalassistants (PDAs), notebooks, etc.) including various other components,such as a battery, speaker, and antennas (not shown).

Aspects described herein may also be operational with numerous othergeneral purpose or special purpose computing system environments orconfigurations. Examples of other computing systems, environments,and/or configurations that may be suitable for use with aspectsdescribed herein include, but are not limited to, personal computers,server computers, hand-held or laptop devices, multiprocessor systems,microprocessor-based systems, set top boxes, programmable consumerelectronics, network personal computers (PCs), minicomputers, mainframecomputers, distributed computing environments that include any of theabove systems or devices, and the like.

As shown in FIG. 2, one or more client devices 240 may be incommunication with one or more servers 206 a-206 n (generally referredto herein as “server(s) 206”). In one embodiment, the computingenvironment 200 may include a network appliance installed between theserver(s) 206 and client machine(s) 240. The network appliance maymanage client/server connections, and in some cases can load balanceclient connections amongst a plurality of backend servers 206.

The client machine(s) 240 may in some embodiments be referred to as asingle client machine 240 or a single group of client machines 240,while server(s) 206 may be referred to as a single server 206 or asingle group of servers 206. In one embodiment a single client machine240 communicates with more than one server 206, while in anotherembodiment a single server 206 communicates with more than one clientmachine 240. In yet another embodiment, a single client machine 240communicates with a single server 206.

A client machine 240 can, in some embodiments, be referenced by any oneof the following non-exhaustive terms: client machine(s); client(s);client computer(s); client device(s); client computing device(s); localmachine; remote machine; client node(s); endpoint(s); or endpointnode(s). The server 206, in some embodiments, may be referenced by anyone of the following non-exhaustive terms: server(s), local machine;remote machine; server farm(s), or host computing device(s).

In one embodiment, the client machine 240 may be a virtual machine. Thevirtual machine may be any virtual machine, while in some embodimentsthe virtual machine may be any virtual machine managed by a Type 1 orType 2 hypervisor, for example, a hypervisor developed by CitrixSystems, IBM, VMware, or any other hypervisor. In some aspects, thevirtual machine may be managed by a hypervisor, while in aspects thevirtual machine may be managed by a hypervisor executing on a server 206or a hypervisor executing on a client 240.

Some embodiments include a client device 240 that displays applicationoutput generated by an application remotely executing on a server 206 orother remotely located machine. In these embodiments, the client device240 may execute a virtual machine receiver program or application todisplay the output in an application window, a browser, or other outputwindow. In one example, the application is a desktop, while in otherexamples the application is an application that generates or presents adesktop. A desktop may include a graphical shell providing a userinterface for an instance of an operating system in which local and/orremote applications can be integrated. Applications, as used herein, areprograms that execute after an instance of an operating system (and,optionally, also the desktop) has been loaded.

The server 206, in some embodiments, uses a remote presentation protocolor other program to send data to a thin-client or remote-displayapplication executing on the client to present display output generatedby an application executing on the server 206. The thin-client orremote-display protocol can be any one of the following non-exhaustivelist of protocols: the Independent Computing Architecture (ICA) protocoldeveloped by Citrix Systems, Inc. of Ft. Lauderdale, Fla.; or the RemoteDesktop Protocol (RDP) manufactured by the Microsoft Corporation ofRedmond, Wash.

A remote computing environment may include more than one server 206a-206 n such that the servers 206 a-206 n are logically grouped togetherinto a server farm 206, for example, in a cloud computing environment.The server farm 206 may include servers 206 that are geographicallydispersed while and logically grouped together, or servers 206 that arelocated proximate to each other while logically grouped together.Geographically dispersed servers 206 a-206 n within a server farm 206can, in some embodiments, communicate using a WAN (wide), MAN(metropolitan), or LAN (local), where different geographic regions canbe characterized as: different continents; different regions of acontinent; different countries; different states; different cities;different campuses; different rooms; or any combination of the precedinggeographical locations. In some embodiments the server farm 206 may beadministered as a single entity, while in other embodiments the serverfarm 206 can include multiple server farms.

In some embodiments, a server farm may include servers 206 that executea substantially similar type of operating system platform (e.g.,WINDOWS, UNIX, LINUX, iOS, ANDROID, SYMBIAN, etc.) In other embodiments,server farm 206 may include a first group of one or more servers thatexecute a first type of operating system platform, and a second group ofone or more servers that execute a second type of operating systemplatform.

Server 206 may be configured as any type of server, as needed, e.g., afile server, an application server, a web server, a proxy server, anappliance, a network appliance, a gateway, an application gateway, agateway server, a virtualization server, a deployment server, a SecureSockets Layer (SSL) VPN server, a firewall, a web server, an applicationserver or as a master application server, a server executing an activedirectory, or a server executing an application acceleration programthat provides firewall functionality, application functionality, or loadbalancing functionality. Other server types may also be used.

Some embodiments include a first server 206 a that receives requestsfrom a client machine 240, forwards the request to a second server 206b, and responds to the request generated by the client machine 240 witha response from the second server 206 b. First server 206 a may acquirean enumeration of applications available to the client machine 240 andwell as address information associated with an application server 206hosting an application identified within the enumeration ofapplications. First server 206 a can then present a response to theclient's request using a web interface, and communicate directly withthe client 240 to provide the client 240 with access to an identifiedapplication. One or more clients 240 and/or one or more servers 206 maytransmit data over network 230, e.g., network 101.

FIG. 3 shows a high-level architecture of an illustrative desktopvirtualization system. As shown, the desktop virtualization system maybe single-server or multi-server system, or cloud system, including atleast one virtualization server 301 configured to provide virtualdesktops and/or virtual applications to one or more client accessdevices 240. As used herein, a desktop refers to a graphical environmentor space in which one or more applications may be hosted and/orexecuted. A desktop may include a graphical shell providing a userinterface for an instance of an operating system in which local and/orremote applications can be integrated. Applications may include programsthat execute after an instance of an operating system (and, optionally,also the desktop) has been loaded. Each instance of the operating systemmay be physical (e.g., one operating system per device) or virtual(e.g., many instances of an OS running on a single device). Eachapplication may be executed on a local device, or executed on a remotelylocated device (e.g., remoted).

A computer device 301 may be configured as a virtualization server in avirtualization environment, for example, a single-server, multi-server,or cloud computing environment. Virtualization server 301 illustrated inFIG. 3 can be deployed as and/or implemented by one or more embodimentsof the server 206 illustrated in FIG. 2 or by other known computingdevices. Included in virtualization server 301 is a hardware layer thatcan include one or more physical disks 304, one or more physical devices306, one or more physical processors 308 and one or more physicalmemories 316. In some embodiments, firmware 312 can be stored within amemory element in the physical memory 316 and can be executed by one ormore of the physical processors 308. Virtualization server 301 mayfurther include an operating system 314 that may be stored in a memoryelement in the physical memory 316 and executed by one or more of thephysical processors 308. Still further, a hypervisor 302 may be storedin a memory element in the physical memory 316 and can be executed byone or more of the physical processors 308.

Executing on one or more of the physical processors 308 may be one ormore virtual machines 332A-C (generally 332). Each virtual machine 332may have a virtual disk 326A-C and a virtual processor 328A-C. In someembodiments, a first virtual machine 332A may execute, using a virtualprocessor 328A, a control program 320 that includes a tools stack 324.Control program 320 may be referred to as a control virtual machine,Dom0, Domain 0, or other virtual machine used for system administrationand/or control. In some embodiments, one or more virtual machines 332B-Ccan execute, using a virtual processor 328B-C, a guest operating system330A-B.

Virtualization server 301 may include a hardware layer 310 with one ormore pieces of hardware that communicate with the virtualization server301. In some embodiments, the hardware layer 310 can include one or morephysical disks 304, one or more physical devices 306, one or morephysical processors 308, and one or more memory 216. Physical components304, 306, 308, and 316 may include, for example, any of the componentsdescribed above. Physical devices 306 may include, for example, anetwork interface card, a video card, a keyboard, a mouse, an inputdevice, a monitor, a display device, speakers, an optical drive, astorage device, a universal serial bus connection, a printer, a scanner,a network element (e.g., router, firewall, network address translator,load balancer, virtual private network (VPN) gateway, Dynamic HostConfiguration Protocol (DHCP) router, etc.), or any device connected toor communicating with virtualization server 301. Physical memory 316 inthe hardware layer 310 may include any type of memory. Physical memory316 may store data, and in some embodiments may store one or moreprograms, or set of executable instructions. FIG. 3 illustrates anembodiment where firmware 312 is stored within the physical memory 316of virtualization server 301. Programs or executable instructions storedin the physical memory 316 can be executed by the one or more processors308 of virtualization server 301.

Virtualization server 301 may also include a hypervisor 302. In someembodiments, hypervisor 302 may be a program executed by processors 308on virtualization server 301 to create and manage any number of virtualmachines 332. Hypervisor 302 may be referred to as a virtual machinemonitor, or platform virtualization software. In some embodiments,hypervisor 302 can be any combination of executable instructions andhardware that monitors virtual machines executing on a computingmachine. Hypervisor 302 may be Type 2 hypervisor, where the hypervisorthat executes within an operating system 314 executing on thevirtualization server 301. Virtual machines then execute at a levelabove the hypervisor. In some embodiments, the Type 2 hypervisorexecutes within the context of a user's operating system such that theType 2 hypervisor interacts with the user's operating system. In otherembodiments, one or more virtualization servers 301 in a virtualizationenvironment may instead include a Type 1 hypervisor (not shown). A Type1 hypervisor may execute on the virtualization server 301 by directlyaccessing the hardware and resources within the hardware layer 310. Thatis, while a Type 2 hypervisor 302 accesses system resources through ahost operating system 314, as shown, a Type 1 hypervisor may directlyaccess all system resources without the host operating system 314. AType 1 hypervisor may execute directly on one or more physicalprocessors 308 of virtualization server 301, and may include programdata stored in the physical memory 316.

Hypervisor 302, in some embodiments, can provide virtual resources tooperating systems 330 or control programs 320 executing on virtualmachines 332 in any manner that simulates the operating systems 330 orcontrol programs 320 having direct access to system resources. Systemresources can include, but are not limited to, physical devices 306,physical disks 304, physical processors 308, physical memory 316 and anyother component included in virtualization server 301 hardware layer310. Hypervisor 302 may be used to emulate virtual hardware, partitionphysical hardware, virtualize physical hardware, and/or execute virtualmachines that provide access to computing environments. In still otherembodiments, hypervisor 302 controls processor scheduling and memorypartitioning for a virtual machine 332 executing on virtualizationserver 301. Hypervisor 302 may include those manufactured by VMWare,Inc., of Palo Alto, Calif.; the XEN hypervisor, an open source productwhose development is overseen by the open source Xen.org community;HyperV, VirtualServer or virtual PC hypervisors provided by Microsoft,or others. In some embodiments, virtualization server 301 executes ahypervisor 302 that creates a virtual machine platform on which guestoperating systems may execute. In these embodiments, the virtualizationserver 301 may be referred to as a host server. An example of such avirtualization server is the XEN SERVER provided by Citrix Systems,Inc., of Fort Lauderdale, Fla.

Hypervisor 302 may create one or more virtual machines 332B-C (generally332) in which guest operating systems 330 execute. In some embodiments,hypervisor 302 may load a virtual machine image to create a virtualmachine 332. In other embodiments, the hypervisor 302 may executes aguest operating system 330 within virtual machine 332. In still otherembodiments, virtual machine 332 may execute guest operating system 330.

In addition to creating virtual machines 332, hypervisor 302 may controlthe execution of at least one virtual machine 332. In other embodiments,hypervisor 302 may presents at least one virtual machine 332 with anabstraction of at least one hardware resource provided by thevirtualization server 301 (e.g., any hardware resource available withinthe hardware layer 310). In other embodiments, hypervisor 302 maycontrol the manner in which virtual machines 332 access physicalprocessors 308 available in virtualization server 301. Controllingaccess to physical processors 308 may include determining whether avirtual machine 332 should have access to a processor 308, and howphysical processor capabilities are presented to the virtual machine332.

As shown in FIG. 3, virtualization server 301 may host or execute one ormore virtual machines 332. A virtual machine 332 is a set of executableinstructions that, when executed by a processor 308, imitate theoperation of a physical computer such that the virtual machine 332 canexecute programs and processes much like a physical computing device.While FIG. 3 illustrates an embodiment where a virtualization server 301hosts three virtual machines 332, in other embodiments virtualizationserver 301 can host any number of virtual machines 332. Hypervisor 302,in some embodiments, provides each virtual machine 332 with a uniquevirtual view of the physical hardware, memory, processor and othersystem resources available to that virtual machine 332. In someembodiments, the unique virtual view can be based on one or more ofvirtual machine permissions, application of a policy engine to one ormore virtual machine identifiers, a user accessing a virtual machine,the applications executing on a virtual machine, networks accessed by avirtual machine, or any other desired criteria. For instance, hypervisor302 may create one or more unsecure virtual machines 332 and one or moresecure virtual machines 332. Unsecure virtual machines 332 may beprevented from accessing resources, hardware, memory locations, andprograms that secure virtual machines 332 may be permitted to access. Inother embodiments, hypervisor 302 may provide each virtual machine 332with a substantially similar virtual view of the physical hardware,memory, processor and other system resources available to the virtualmachines 332.

Each virtual machine 332 may include a virtual disk 326A-C (generally326) and a virtual processor 328A-C (generally 328.) The virtual disk326, in some embodiments, is a virtualized view of one or more physicaldisks 304 of the virtualization server 301, or a portion of one or morephysical disks 304 of the virtualization server 301. The virtualizedview of the physical disks 304 can be generated, provided and managed bythe hypervisor 302. In some embodiments, hypervisor 302 provides eachvirtual machine 332 with a unique view of the physical disks 304. Thus,in these embodiments, the particular virtual disk 326 included in eachvirtual machine 332 can be unique when compared with the other virtualdisks 326.

A virtual processor 328 can be a virtualized view of one or morephysical processors 308 of the virtualization server 301. In someembodiments, the virtualized view of the physical processors 308 can begenerated, provided and managed by hypervisor 302. In some embodiments,virtual processor 328 has substantially all of the same characteristicsof at least one physical processor 308. In other embodiments, virtualprocessor 308 provides a modified view of physical processors 308 suchthat at least some of the characteristics of the virtual processor 328are different than the characteristics of the corresponding physicalprocessor 308.

With further reference to FIG. 4, some aspects described herein may beimplemented in a cloud-based environment. FIG. 4 illustrates an exampleof a cloud computing environment (or cloud system) 400. As seen in FIG.4, client computers 411-414 may communicate with a cloud managementserver 410 to access the computing resources (e.g., host servers 403,storage resources 404, and network resources 405) of the cloud system.

Management server 410 may be implemented on one or more physicalservers. The management server 410 may run, for example, CLOUDSTACK byCitrix Systems, Inc. of Ft. Lauderdale, Fla., or OPENSTACK, amongothers. Management server 410 may manage various computing resources,including cloud hardware and software resources, for example, hostcomputers 403, data storage devices 404, and networking devices 405. Thecloud hardware and software resources may include private and/or publiccomponents. For example, a cloud may be configured as a private cloud tobe used by one or more particular customers or client computers 411-414and/or over a private network. In other embodiments, public clouds orhybrid public-private clouds may be used by other customers over an openor hybrid networks.

Management server 410 may be configured to provide user interfacesthrough which cloud operators and cloud customers may interact with thecloud system. For example, the management server 410 may provide a setof application programming interfaces (APIs) and/or one or more cloudoperator console applications (e.g., web-based on standaloneapplications) with user interfaces to allow cloud operators to managethe cloud resources, configure the virtualization layer, manage customeraccounts, and perform other cloud administration tasks. The managementserver 410 also may include a set of APIs and/or one or more customerconsole applications with user interfaces configured to receive cloudcomputing requests from end users via client computers 411-414, forexample, requests to create, modify, or destroy virtual machines withinthe cloud. Client computers 411-414 may connect to management server 410via the Internet or other communication network, and may request accessto one or more of the computing resources managed by management server410. In response to client requests, the management server 410 mayinclude a resource manager configured to select and provision physicalresources in the hardware layer of the cloud system based on the clientrequests. For example, the management server 410 and additionalcomponents of the cloud system may be configured to provision, create,and manage virtual machines and their operating environments (e.g.,hypervisors, storage resources, services offered by the networkelements, etc.) for customers at client computers 411-414, over anetwork (e.g., the Internet), providing customers with computationalresources, data storage services, networking capabilities, and computerplatform and application support. Cloud systems also may be configuredto provide various specific services, including security systems,development environments, user interfaces, and the like.

Certain clients 411-414 may be related, for example, different clientcomputers creating virtual machines on behalf of the same end user, ordifferent users affiliated with the same company or organization. Inother examples, certain clients 411-414 may be unrelated, such as usersaffiliated with different companies or organizations. For unrelatedclients, information on the virtual machines or storage of any one usermay be hidden from other users.

Referring now to the physical hardware layer of a cloud computingenvironment, availability zones 401-402 (or zones) may refer to acollocated set of physical computing resources. Zones may begeographically separated from other zones in the overall cloud ofcomputing resources. For example, zone 401 may be a first clouddatacenter located in California, and zone 402 may be a second clouddatacenter located in Florida. Management sever 410 may be located atone of the availability zones, or at a separate location. Each zone mayinclude an internal network that interfaces with devices that areoutside of the zone, such as the management server 410, through agateway. End users of the cloud (e.g., clients 411-414) might or mightnot be aware of the distinctions between zones. For example, an end usermay request the creation of a virtual machine having a specified amountof memory, processing power, and network capabilities. The managementserver 410 may respond to the user's request and may allocate theresources to create the virtual machine without the user knowing whetherthe virtual machine was created using resources from zone 401 or zone402. In other examples, the cloud system may allow end users to requestthat virtual machines (or other cloud resources) are allocated in aspecific zone or on specific resources 403-405 within a zone.

In this example, each zone 401-402 may include an arrangement of variousphysical hardware components (or computing resources) 403-405, forexample, physical hosting resources (or processing resources), physicalnetwork resources, physical storage resources, switches, and additionalhardware resources that may be used to provide cloud computing servicesto customers. The physical hosting resources in a cloud zone 401-402 mayinclude one or more computer servers 403, such as the virtualizationservers 301 described above, which may be configured to create and hostvirtual machine instances. The physical network resources in a cloudzone 401 or 402 may include one or more network elements 405 (e.g.,network service providers) comprising hardware and/or softwareconfigured to provide a network service to cloud customers, such asfirewalls, network address translators, load balancers, virtual privatenetwork (VPN) gateways, Dynamic Host Configuration Protocol (DHCP)routers, and the like. The storage resources in the cloud zone 401-402may include storage disks (e.g., solid state drives (SSDs), magnetichard disks, etc.) and other storage devices.

The example cloud computing environment shown in FIG. 4 also may includea virtualization layer (e.g., as shown in FIGS. 1-3) with additionalhardware and/or software resources configured to create and managevirtual machines and provide other services to customers using thephysical resources in the cloud. The virtualization layer may includehypervisors, as described above in FIG. 3, along with other componentsto provide network virtualizations, storage virtualizations, etc. Thevirtualization layer may be as a separate layer from the physicalresource layer, or may share some or all of the same hardware and/orsoftware resources with the physical resource layer. For example, thevirtualization layer may include a hypervisor installed in each of thevirtualization servers 403 with the physical computing resources. Knowncloud systems may alternatively be used, e.g., WINDOWS AZURE (MicrosoftCorporation of Redmond Wash.), AMAZON EC2 (Amazon.com Inc. of Seattle,Wash.), IBM BLUE CLOUD (IBM Corporation of Armonk, N.Y.), or others.

Enterprise Mobility Management Architecture

FIG. 5 represents an enterprise mobility technical architecture 500 foruse in a BYOD environment. The architecture enables a user of a mobiledevice 502 to both access enterprise or personal resources from a mobiledevice 502 and use the mobile device 502 for personal use. The user mayaccess such enterprise resources 504 or enterprise services 508 using amobile device 502 that is purchased by the user or a mobile device 502that is provided by the enterprise to user. The user may utilize themobile device 502 for business use only or for business and personaluse. The mobile device may run an iOS operating system, an Androidoperating system, or the like. The enterprise may choose to implementpolicies to manage the mobile device 504. The policies may be implantedthrough a firewall or gateway in such a way that the mobile device maybe identified, secured or security verified, and provided selective orfull access to the enterprise resources. The policies may be mobiledevice management policies, mobile application management policies,mobile data management policies, or some combination of mobile device,application, and data management policies. A mobile device 504 that ismanaged through the application of mobile device management policies maybe referred to as an enrolled device.

In some embodiments, the operating system of the mobile device may beseparated into a managed partition 510 and an unmanaged partition 512.The managed partition 510 may have policies applied to it to secure theapplications running on and data stored in the managed partition. Theapplications running on the managed partition may be secureapplications. In other embodiments, all applications may execute inaccordance with a set of one or more policy files received separate fromthe application, and which define one or more security parameters,features, resource restrictions, and/or other access controls that areenforced by the mobile device management system when that application isexecuting on the device. By operating in accordance with theirrespective policy file(s), each application may be allowed or restrictedfrom communications with one or more other applications and/orresources, thereby creating a virtual partition. Thus, as used herein, apartition may refer to a physically partitioned portion of memory(physical partition), a logically partitioned portion of memory (logicalpartition), and/or a virtual partition created as a result ofenforcement of one or more policies and/or policy files across multipleapps as described herein (virtual partition). Stated differently, byenforcing policies on managed apps, those apps may be restricted to onlybe able to communicate with other managed apps and trusted enterpriseresources, thereby creating a virtual partition that is impenetrable byunmanaged apps and devices.

The secure applications may be email applications, web browsingapplications, software-as-a-service (SaaS) access applications, WindowsApplication access applications, and the like. The secure applicationsmay be secure native applications 514, secure remote applications 522executed by a secure application launcher 518, virtualizationapplications 526 executed by a secure application launcher 518, and thelike. The secure native applications 514 may be wrapped by a secureapplication wrapper 520. The secure application wrapper 520 may includeintegrated policies that are executed on the mobile device 502 when thesecure native application is executed on the device. The secureapplication wrapper 520 may include meta-data that points the securenative application 514 running on the mobile device 502 to the resourceshosted at the enterprise that the secure native application 514 mayrequire to complete the task requested upon execution of the securenative application 514. The secure remote applications 522 executed by asecure application launcher 518 may be executed within the secureapplication launcher application 518. The virtualization applications526 executed by a secure application launcher 518 may utilize resourceson the mobile device 502, at the enterprise resources 504, and the like.The resources used on the mobile device 502 by the virtualizationapplications 526 executed by a secure application launcher 518 mayinclude user interaction resources, processing resources, and the like.The user interaction resources may be used to collect and transmitkeyboard input, mouse input, camera input, tactile input, audio input,visual input, gesture input, and the like. The processing resources maybe used to present a user interface, process data received from theenterprise resources 504, and the like. The resources used at theenterprise resources 504 by the virtualization applications 526 executedby a secure application launcher 518 may include user interfacegeneration resources, processing resources, and the like. The userinterface generation resources may be used to assemble a user interface,modify a user interface, refresh a user interface, and the like. Theprocessing resources may be used to create information, readinformation, update information, delete information, and the like. Forexample, the virtualization application may record user interactionsassociated with a graphical user interface (GUI) and communicate them toa server application where the server application will use the userinteraction data as an input to the application operating on the server.In this arrangement, an enterprise may elect to maintain the applicationon the server side as well as data, files, etc. associated with theapplication. While an enterprise may elect to “mobilize” someapplications in accordance with the principles herein by securing themfor deployment on the mobile device, this arrangement may also beelected for certain applications. For example, while some applicationsmay be secured for use on the mobile device, others might not beprepared or appropriate for deployment on the mobile device so theenterprise may elect to provide the mobile user access to the unpreparedapplications through virtualization techniques. As another example, theenterprise may have large complex applications with large and complexdata sets (e.g., material resource planning applications) where it wouldbe very difficult, or otherwise undesirable, to customize theapplication for the mobile device so the enterprise may elect to provideaccess to the application through virtualization techniques. As yetanother example, the enterprise may have an application that maintainshighly secured data (e.g., human resources data, customer data,engineering data) that may be deemed by the enterprise as too sensitivefor even the secured mobile environment so the enterprise may elect touse virtualization techniques to permit mobile access to suchapplications and data. An enterprise may elect to provide both fullysecured and fully functional applications on the mobile device as wellas a virtualization application to allow access to applications that aredeemed more properly operated on the server side. In an embodiment, thevirtualization application may store some data, files, etc. on themobile phone in one of the secure storage locations. An enterprise, forexample, may elect to allow certain information to be stored on thephone while not permitting other information.

In connection with the virtualization application, as described herein,the mobile device may have a virtualization application that is designedto present GUIs and then record user interactions with the GUI. Theapplication may communicate the user interactions to the server side tobe used by the server side application as user interactions with theapplication. In response, the application on the server side maytransmit back to the mobile device a new GUI. For example, the new GUImay be a static page, a dynamic page, an animation, or the like, therebyproviding access to remotely located resources.

The secure applications may access data stored in a secure datacontainer 528 in the managed partition 510 of the mobile device. Thedata secured in the secure data container may be accessed by the securewrapped applications 514, applications executed by a secure applicationlauncher 522, virtualization applications 526 executed by a secureapplication launcher 522, and the like. The data stored in the securedata container 528 may include files, databases, and the like. The datastored in the secure data container 528 may include data restricted to aspecific secure application 530, shared among secure applications 532,and the like. Data restricted to a secure application may include securegeneral data 534 and highly secure data 538. Secure general data may usea strong form of encryption such as Advanced Encryption Standard (AES)128-bit encryption or the like, while highly secure data 538 may use avery strong form of encryption such as AES 256-bit encryption. Datastored in the secure data container 528 may be deleted from the deviceupon receipt of a command from the device manager 524. The secureapplications may have a dual-mode option 540. The dual mode option 540may present the user with an option to operate the secured applicationin an unsecured or unmanaged mode. In an unsecured or unmanaged mode,the secure applications may access data stored in an unsecured datacontainer 542 on the unmanaged partition 512 of the mobile device 502.The data stored in an unsecured data container may be personal data 544.The data stored in an unsecured data container 542 may also be accessedby unsecured applications 548 that are running on the unmanagedpartition 512 of the mobile device 502. The data stored in an unsecureddata container 542 may remain on the mobile device 502 when the datastored in the secure data container 528 is deleted from the mobiledevice 502. An enterprise may want to delete from the mobile deviceselected or all data, files, and/or applications owned, licensed orcontrolled by the enterprise (enterprise data) while leaving orotherwise preserving personal data, files, and/or applications owned,licensed or controlled by the user (personal data). This operation maybe referred to as a selective wipe. With the enterprise and personaldata arranged in accordance to the aspects described herein, anenterprise may perform a selective wipe.

The mobile device may connect to enterprise resources 504 and enterpriseservices 508 at an enterprise, to the public Internet 548, and the like.The mobile device may connect to enterprise resources 504 and enterpriseservices 508 through virtual private network connections. The virtualprivate network connections, also referred to as microVPN orapplication-specific VPN, may be specific to particular applications550, particular devices, particular secured areas on the mobile device,and the like 552. For example, each of the wrapped applications in thesecured area of the phone may access enterprise resources through anapplication specific VPN such that access to the VPN would be grantedbased on attributes associated with the application, possibly inconjunction with user or device attribute information. The virtualprivate network connections may carry Microsoft Exchange traffic,Microsoft Active Directory traffic, HyperText Transfer Protocol (HTTP)traffic, HyperText Transfer Protocol Secure (HTTPS) traffic, applicationmanagement traffic, and the like. The virtual private networkconnections may support and enable single-sign-on authenticationprocesses 554. The single-sign-on processes may allow a user to providea single set of authentication credentials, which are then verified byan authentication service 558. The authentication service 558 may thengrant to the user access to multiple enterprise resources 504, withoutrequiring the user to provide authentication credentials to eachindividual enterprise resource 504.

The virtual private network connections may be established and managedby an access gateway 560. The access gateway 560 may include performanceenhancement features that manage, accelerate, and improve the deliveryof enterprise resources 504 to the mobile device 502. The access gatewaymay also re-route traffic from the mobile device 502 to the publicInternet 548, enabling the mobile device 502 to access publiclyavailable and unsecured applications that run on the public Internet548. The mobile device may connect to the access gateway via a transportnetwork 562. The transport network 562 may be a wired network, wirelessnetwork, cloud network, local area network, metropolitan area network,wide area network, public network, private network, and the like.

The enterprise resources 504 may include email servers, file sharingservers, SaaS applications, Web application servers, Windows applicationservers, and the like. Email servers may include Exchange servers, LotusNotes servers, and the like. File sharing servers may include ShareFileservers, and the like. SaaS applications may include Salesforce, and thelike. Windows application servers may include any application serverthat is built to provide applications that are intended to run on alocal Windows operating system, and the like. The enterprise resources504 may be premise-based resources, cloud based resources, and the like.The enterprise resources 504 may be accessed by the mobile device 502directly or through the access gateway 560. The enterprise resources 504may be accessed by the mobile device 502 via a transport network 562.The transport network 562 may be a wired network, wireless network,cloud network, local area network, metropolitan area network, wide areanetwork, public network, private network, and the like.

The enterprise services 508 may include authentication services 558,threat detection services 564, device manager services 524, file sharingservices 568, policy manager services 570, social integration services572, application controller services 574, and the like. Authenticationservices 558 may include user authentication services, deviceauthentication services, application authentication services, dataauthentication services and the like. Authentication services 558 mayuse certificates. The certificates may be stored on the mobile device502, by the enterprise resources 504, and the like. The certificatesstored on the mobile device 502 may be stored in an encrypted locationon the mobile device, the certificate may be temporarily stored on themobile device 502 for use at the time of authentication, and the like.Threat detection services 564 may include intrusion detection services,unauthorized access attempt detection services, and the like.Unauthorized access attempt detection services may include unauthorizedattempts to access devices, applications, data, and the like. Devicemanagement services 524 may include configuration, provisioning,security, support, monitoring, reporting, and decommissioning services.File sharing services 568 may include file management services, filestorage services, file collaboration services, and the like. Policymanager services 570 may include device policy manager services,application policy manager services, data policy manager services, andthe like. Social integration services 572 may include contactintegration services, collaboration services, integration with socialnetworks such as Facebook, Twitter, and LinkedIn, and the like.Application controller services 574 may include management services,provisioning services, deployment services, assignment services,revocation services, wrapping services, and the like.

The enterprise mobility technical architecture 500 may include anapplication store 578. The application store 578 may include unwrappedapplications 580, pre-wrapped applications 582, and the like.Applications may be populated in the application store 578 from theapplication controller 574. The application store 578 may be accessed bythe mobile device 502 through the access gateway 560, through the publicInternet 548, or the like. The application store may be provided with anintuitive and easy to use User Interface.

A software development kit 584 may provide a user the capability tosecure applications selected by the user by wrapping the application asdescribed previously in this description. An application that has beenwrapped using the software development kit 584 may then be madeavailable to the mobile device 502 by populating it in the applicationstore 578 using the application controller 574.

The enterprise mobility technical architecture 500 may include amanagement and analytics capability 588. The management and analyticscapability 588 may provide information related to how resources areused, how often resources are used, and the like. Resources may includedevices, applications, data, and the like. How resources are used mayinclude which devices download which applications, which applicationsaccess which data, and the like. How often resources are used mayinclude how often an application has been downloaded, how many times aspecific set of data has been accessed by an application, and the like.

FIG. 6 is another illustrative enterprise mobility management system600. Some of the components of the mobility management system 500described above with reference to FIG. 5 have been omitted for the sakeof simplicity. The architecture of the system 600 depicted in FIG. 6 issimilar in many respects to the architecture of the system 500 describedabove with reference to FIG. 5 and may include additional features notmentioned above.

In this case, the left hand side represents an enrolled mobile device602 with a client agent 604, which interacts with gateway server 606(which includes Access Gateway and application controller functionality)to access various enterprise resources 608 and services 609 such asExchange, Sharepoint, public-key infrastructure (PKI) Resources,Kerberos Resources, Certificate Issuance service, as shown on the righthand side above. Although not specifically shown, the mobile device 602may also interact with an enterprise application store (StoreFront) forthe selection and downloading of applications.

The client agent 604 acts as the UI (user interface) intermediary forWindows apps/desktops hosted in an Enterprise data center, which areaccessed using the High-Definition User Experience (HDX)/ICA displayremoting protocol. The client agent 604 also supports the installationand management of native applications on the mobile device 602, such asnative iOS or Android applications. For example, the managedapplications 610 (mail, browser, wrapped application) shown in thefigure above are all native applications that execute locally on thedevice. Client agent 604 and application management framework of thisarchitecture act to provide policy driven management capabilities andfeatures such as connectivity and SSO (single sign on) to enterpriseresources/services 608. The client agent 604 handles primary userauthentication to the enterprise, normally to Access Gateway (AG) withSSO to other gateway server components. The client agent 604 obtainspolicies from gateway server 606 to control the behavior of the managedapplications 610 on the mobile device 602.

The Secure interprocess communication (IPC) links 612 between the nativeapplications 610 and client agent 604 represent a management channel,which allows client agent to supply policies to be enforced by theapplication management framework 614 “wrapping” each application. TheIPC channel 612 also allows client agent 604 to supply credential andauthentication information that enables connectivity and SSO toenterprise resources 608. Finally the IPC channel 612 allows theapplication management framework 614 to invoke user interface functionsimplemented by client agent 604, such as online and offlineauthentication.

Communications between the client agent 604 and gateway server 606 areessentially an extension of the management channel from the applicationmanagement framework 614 wrapping each native managed application 610.The application management framework 614 requests policy informationfrom client agent 604, which in turn requests it from gateway server606. The application management framework 614 requests authentication,and client agent 604 logs into the gateway services part of gatewayserver 606 (also known as NetScaler Access Gateway). Client agent 604may also call supporting services on gateway server 606, which mayproduce input material to derive encryption keys for the local datavaults 616, or provide client certificates which may enable directauthentication to PKI protected resources, as more fully explainedbelow.

In more detail, the application management framework 614 “wraps” eachmanaged application 610. This may be incorporated via an explicit buildstep, or via a post-build processing step. The application managementframework 614 may “pair” with client agent 604 on first launch of anapplication 610 to initialize the Secure IPC channel and obtain thepolicy for that application. The application management framework 614may enforce relevant portions of the policy that apply locally, such asthe client agent login dependencies and some of the containment policiesthat restrict how local OS services may be used, or how they mayinteract with the application 610.

The application management framework 614 may use services provided byclient agent 604 over the Secure IPC channel 612 to facilitateauthentication and internal network access. Key management for theprivate and shared data vaults 616 (containers) may be also managed byappropriate interactions between the managed applications 610 and clientagent 604. Vaults 616 may be available only after online authentication,or may be made available after offline authentication if allowed bypolicy. First use of vaults 616 may require online authentication, andoffline access may be limited to at most the policy refresh periodbefore online authentication is again required.

Network access to internal resources may occur directly from individualmanaged applications 610 through Access Gateway 606. The applicationmanagement framework 614 is responsible for orchestrating the networkaccess on behalf of each application 610. Client agent 604 mayfacilitate these network connections by providing suitable time limitedsecondary credentials obtained following online authentication. Multiplemodes of network connection may be used, such as reverse web proxyconnections and end-to-end VPN-style tunnels 618.

The Mail and Browser managed applications 610 have special status andmay make use of facilities that might not be generally available toarbitrary wrapped applications. For example, the Mail application mayuse a special background network access mechanism that allows it toaccess Exchange over an extended period of time without requiring a fullAG logon. The Browser application may use multiple private data vaultsto segregate different kinds of data.

This architecture supports the incorporation of various other securityfeatures. For example, gateway server 606 (including its gatewayservices) in some cases will not need to validate active directory (AD)passwords. It can be left to the discretion of an enterprise whether anAD password is used as an authentication factor for some users in somesituations. Different authentication methods may be used if a user isonline or offline (i.e., connected or not connected to a network).

Step up authentication is a feature wherein gateway server 606 mayidentify managed native applications 610 that are allowed to have accessto highly classified data requiring strong authentication, and ensurethat access to these applications is only permitted after performingappropriate authentication, even if this means a re-authentication isrequired by the user after a prior weaker level of login.

Another security feature of this solution is the encryption of the datavaults 616 (containers) on the mobile device 602. The vaults 616 may beencrypted so that all on-device data including files, databases, andconfigurations are protected. For on-line vaults, the keys may be storedon the server (gateway server 606), and for off-line vaults, a localcopy of the keys may be protected by a user password or biometricvalidation. When data is stored locally on the device 602 in the securecontainer 616, it is preferred that a minimum of AES 256 encryptionalgorithm be utilized.

Other secure container features may also be implemented. For example, alogging feature may be included, wherein all security events happeninginside an application 610 are logged and reported to the backend. Datawiping may be supported, such as if the application 610 detectstampering, associated encryption keys may be written over with randomdata, leaving no hint on the file system that user data was destroyed.Screenshot protection is another feature, where an application mayprevent any data from being stored in screenshots. For example, the keywindow's hidden property may be set to YES. This may cause whatevercontent is currently displayed on the screen to be hidden, resulting ina blank screenshot where any content would normally reside.

Local data transfer may be prevented, such as by preventing any datafrom being locally transferred outside the application container, e.g.,by copying it or sending it to an external application. A keyboard cachefeature may operate to disable the autocorrect functionality forsensitive text fields. SSL certificate validation may be operable so theapplication specifically validates the server SSL certificate instead ofit being stored in the keychain. An encryption key generation featuremay be used such that the key used to encrypt data on the device isgenerated using a passphrase or biometric data supplied by the user (ifoffline access is required). It may be XORed with another key randomlygenerated and stored on the server side if offline access is notrequired. Key Derivation functions may operate such that keys generatedfrom the user password use KDFs (key derivation functions, notablyPassword-Based Key Derivation Function 2 (PBKDF2)) rather than creatinga cryptographic hash of it. The latter makes a key susceptible to bruteforce or dictionary attacks.

Further, one or more initialization vectors may be used in encryptionmethods. An initialization vector will cause multiple copies of the sameencrypted data to yield different cipher text output, preventing bothreplay and cryptanalytic attacks. This will also prevent an attackerfrom decrypting any data even with a stolen encryption key if thespecific initialization vector used to encrypt the data is not known.Further, authentication then decryption may be used, wherein applicationdata is decrypted only after the user has authenticated within theapplication. Another feature may relate to sensitive data in memory,which may be kept in memory (and not in disk) only when it's needed. Forexample, login credentials may be wiped from memory after login, andencryption keys and other data inside objective-C instance variables arenot stored, as they may be easily referenced. Instead, memory may bemanually allocated for these.

An inactivity timeout may be implemented, wherein after a policy-definedperiod of inactivity, a user session is terminated.

Data leakage from the application management framework 614 may beprevented in other ways. For example, when an application 610 is put inthe background, the memory may be cleared after a predetermined(configurable) time period. When backgrounded, a snapshot may be takenof the last displayed screen of the application to fasten theforegrounding process. The screenshot may contain confidential data andhence should be cleared.

Another security feature relates to the use of an OTP (one timepassword) 620 without the use of an AD (active directory) 622 passwordfor access to one or more applications. In some cases, some users do notknow (or are not permitted to know) their AD password, so these usersmay authenticate using an OTP 620 such as by using a hardware OTP systemlike SecurID (OTPs may be provided by different vendors also, such asEntrust or Gemalto). In some cases, after a user authenticates with auser ID, a text is sent to the user with an OTP 620. In some cases, thismay be implemented only for online use, with a prompt being a singlefield.

An offline password may be implemented for offline authentication forthose applications 610 for which offline use is permitted via enterprisepolicy. For example, an enterprise may want StoreFront to be accessed inthis manner. In this case, the client agent 604 may require the user toset a custom offline password and the AD password is not used. Gatewayserver 606 may provide policies to control and enforce passwordstandards with respect to the minimum length, character classcomposition, and age of passwords, such as described by the standardWindows Server password complexity requirements, although theserequirements may be modified.

Another feature relates to the enablement of a client side certificatefor certain applications 610 as secondary credentials (for the purposeof accessing PKI protected web resources via the application managementframework micro VPN feature). For example, an application may utilizesuch a certificate. In this case, certificate-based authentication usingActiveSync protocol may be supported, wherein a certificate from theclient agent 604 may be retrieved by gateway server 606 and used in akeychain. Each managed application may have one associated clientcertificate, identified by a label that is defined in gateway server606.

Gateway server 606 may interact with an Enterprise special purpose webservice to support the issuance of client certificates to allow relevantmanaged applications to authenticate to internal PKI protectedresources.

The client agent 604 and the application management framework 614 may beenhanced to support obtaining and using client certificates forauthentication to internal PKI protected network resources. More thanone certificate may be supported, such as to match various levels ofsecurity and/or separation requirements. The certificates may be used bythe Mail and Browser managed applications, and ultimately by arbitrarywrapped applications (provided those applications use web service stylecommunication patterns where it is reasonable for the applicationmanagement framework to mediate https requests).

Application management client certificate support on iOS may rely onimporting a public-key cryptography standards (PKCS) 12 BLOB (BinaryLarge Object) into the iOS keychain in each managed application for eachperiod of use. Application management framework client certificatesupport may use a HTTPS implementation with private in-memory keystorage. The client certificate will never be present in the iOSkeychain and will not be persisted except potentially in “online-only”data value that is strongly protected.

Mutual SSL may also be implemented to provide additional security byrequiring that a mobile device 602 is authenticated to the enterprise,and vice versa. Virtual smart cards for authentication to gateway server606 may also be implemented.

Both limited and full Kerberos support may be additional features. Thefull support feature relates to an ability to do full Kerberos login toActive Directory (AD) 622, using an AD password or trusted clientcertificate, and obtain Kerberos service tickets to respond to HTTPNegotiate authentication challenges. The limited support feature relatesto constrained delegation in Citrix Access Gateway Enterprise Edition(AGEE), where AGEE supports invoking Kerberos protocol transition so itcan obtain and use Kerberos service tickets (subject to constraineddelegation) in response to HTTP Negotiate authentication challenges.This mechanism works in reverse web proxy (aka corporate virtual privatenetwork (CVPN)) mode, and when http (but not https) connections areproxied in VPN and MicroVPN mode.

Another feature relates to application container locking and wiping,which may automatically occur upon jail-break or rooting detections, andoccur as a pushed command from administration console, and may include aremote wipe functionality even when an application 610 is not running.

A multi-site architecture or configuration of enterprise applicationstore and an application controller may be supported that allows usersto be service from one of several different locations in case offailure.

In some cases, managed applications 610 may be allowed to access acertificate and private key via an API (example OpenSSL). Trustedmanaged applications 610 of an enterprise may be allowed to performspecific Public Key operations with an application's client certificateand private key. Various use cases may be identified and treatedaccordingly, such as when an application behaves like a browser and nocertificate access is required, when an application reads a certificatefor “who am I,” when an application uses the certificate to build asecure session token, and when an application uses private keys fordigital signing of important data (e.g. transaction log) or fortemporary data encryption.

Using Derived Credentials for Enrollment with Enterprise Mobile DeviceManagement Services

Having discussed several examples of the computing architecture that maybe used in providing and/or implementing various aspects of thedisclosure, a number of embodiments will now be discussed in greaterdetail. In particular, and as introduced above, some aspects of thedisclosure generally relate to enrolling a mobile computing device withan enterprise mobile device management system using derived credentials.In the description below, various examples illustrating how a mobilecomputing device may be enrolled with an enterprise mobile devicemanagement system in accordance with one or more embodiments will bediscussed.

FIG. 7 depicts an illustrative system architecture in which a mobilecomputing device 710 may enroll with an enterprise mobile devicemanagement server 724 in order to access enterprise resources 720. Thearchitecture of the system depicted in FIG. 7 is similar in manyrespects to the architecture of the systems 500 and 600 described abovewith reference to FIGS. 5 and 6 and may include additional features notmentioned above. Some of the components of the mobility managementsystems 500 and 600 described above with reference to FIGS. 5 and 6 havebeen omitted for the sake of simplicity.

The enrollment application 712 may in one embodiment be launched inresponse to a user command. A user of the mobile computing device 710may have been instructed to initiate the enrollment process by startingthe enrollment application 712. The enrollment application 712 may beconfigured to prompt the user of the mobile computing device 710 for ausername. In some embodiments, the username may comprise the UserPrincipal Name (UPN). The enrollment application 712 may be furtherconfigured to prompt the user of the mobile computing device 710 for thenetwork address of the enterprise mobile device management server 724.In some embodiments, the network address of the enterprise mobile devicemanagement server 724 may comprise a Uniform Record Locator (URL)address. In other embodiments, the network address of the enterprisemobile device management server 724 may comprise an Internet Protocol(IP) address.

The automatic discovery server 722 may be a single-server ormulti-server system, or a cloud-based system, including at least onevirtualization server, as described above with reference to FIG. 4. Theenrollment application 712 may access the automatic discovery server 722via a network 730. The network 730 may be a wired network, wirelessnetwork, cloud network, local area network, metropolitan area network,wide area network, public network, private network, and the like. Theenrollment application 712 may be configured to generate configurationinformation request messages. The configuration information requestmessages may comprise the username and/or the network address of theenterprise mobile device management server 724 as provided by the userof the mobile computing device 710. The enrollment application 712 maytransmit these configuration information request messages to theautomatic discovery server 722 via a network 730. The automaticdiscovery server 722 may be configured to respond to the configurationinformation request messages from the enrollment application 712 with amessage comprising the configuration information for the enterprisemobile device management server 724. The configuration information maycomprise redirection information and/or setup flags to be used tocommunicate with the enterprise mobile device management server 724. Theautomatic discovery server 722 may determine its response to theconfiguration request message based on the username or the networkaddress of the enterprise mobile device management server 724 comprisedin the configuration request message.

The enterprise mobile device management server 724 may be asingle-server or multi-server system, or a cloud-based system, includingat least one virtualization server, as described above with reference toFIG. 4. An example of such a mobile device management server is theXENMOBILE server manufactured by Citrix Systems, Inc., of FortLauderdale, Fla. The enrollment application 712 may access theenterprise mobile device management server 724 via a network 730. Theenrollment application 712 may be configured to send an enrollmentrequest message to the enterprise mobile device management server 724.In some embodiments, the enrollment application 712 may address theenrollment request message using the network address to the enterprisemobile device management server 724 provided by the user. In otherembodiments, the enrollment application 712 may address the enrollmentrequest message using the configuration information received from theautomatic discovery server 722. The enterprise mobile device managementserver 724 may be configured to respond to the enrollment requestmessage with a response message comprising derived credentialinformation, certificate management system application information, andpassword complexity rule information.

With further reference to FIG. 7, the enrollment application 712 may beconfigured to prompt the user of the mobile computing device 710 for auser password based on the password complexity rule informationcomprised in the enrollment request response message received from theenterprise mobile device management server 724. The user password mightbe a secret or password that is known only to the user of the mobilecomputing device 710. The user password might not be the user's networkor directory service password. The user password may be used to protectthe derived credentials stored in the mobile computing device 710, asdescribed in greater detail below. The enrollment application 712 may beconfigured to derive a password validation value generated from the userpassword. In some embodiments, the password validation value may begenerated using KDFs (key derivation functions, notably Password-BasedKey Derivation Function 2 (PBKDF2)) rather than creating a cryptographichash of the user password. The latter makes a key susceptible to bruteforce or dictionary attacks. The password-based key value may then beencrypted using a very strong form of encryption such as AdvancedEncryption Standard (AES) 256-bit encryption or the like. The enrollmentapplication 712 may store the resulting password validation value in ashared vault 716 on the mobile computing device 710. The enrollmentapplication 712 might not store the user password in the shared vault716.

The mobile computing device 710 may run an iOS operating system, anAndroid operating system, or the like. The shared vault 716 may in oneembodiment be a shared keychain in an iOS-based mobile computing device;in another embodiment the shared vault 716 may be a shared contentprovider in an Android-based mobile computing device; and, in yetanother embodiment, the shared vault 716 may be a shared data vault asdescribed above with reference to FIG. 6. In some embodiments, allapplications that access the shared vault 716, like the enrollmentapplication 712 and the certificate management system application 714,may be digitally signed with the same development signing certificate.Applications that share the same development signing certificate may beallowed to share the data stored in the shared vault 716.

The certificate management system sever 728 may be accessed by thecertificate management system application 714 via a network 730. Thecertificate management system server 728 may be a single-server ormulti-server system, or a cloud-based system, including at least onevirtualization server, as described above with reference to FIG. 4. Thecertificate management system can be any one of the followingnon-exhaustive list of products: MyID manufactured by Intercede GroupPlc. of Leicestershire, United Kingdom; or IdentityGuard™ manufacturedby the Entrust Datacard Corporation of Minneapolis, Minn. The enrollmentapplication 712 may launch the certificate management system application714 and cause the mobile computing device 710 to switch control to thecertificate management system application 714. As part of the launchcommand, the enrollment application 712 may provide the user passwordreceived from the user of the mobile computing device 710 to thecertificate management system application 714. In some embodiments, theenrollment application 712 may launch the certificate management systemapplication 714 by means of a Uniform Resource Locator (URL) addresswhich comprises the user password. The enrollment application 712 mayidentify the certificate management system application 714 to launchbased on the certificate management system application informationcomprised in the enrollment request response message received from theenterprise mobile device management server 724. If or when thecertificate management system application 714 identified by theenrollment application 712 is not installed on the mobile computingdevice 710, then the enrollment application 712 may be configured tolaunch an application store (not shown in FIG. 7) on the mobilecomputing device 710, or access an application store 578 as describedabove in reference to FIG. 5, and prompt the user of the mobilecomputing device 710 to install the certificate management systemapplication 714.

The directory service 726 may be single-server or multi-server system,or a cloud-based system, including at least one virtualization server,as described above with reference to FIG. 4. The directory service 726may be a server configured to authenticate and authorize users anddevices in an enterprise, like Microsoft Active Directory, manufacturedby the Microsoft Corporation of Redmond, Wash.

The certificate management system application 714 may be configured toauthenticate the user of the mobile computing device and the mobilecomputing device with the certificate management system server 728. Thecertificate management system application 714 may use at least one ormore authentication mechanisms to authenticate with the certificatemanagement system server 728, as required by the enterprise. In oneembodiment, the authentication may be performed remotely. In anotherembodiment, the authentication may be performed in person at a kiosk 740and may include biometric authentication. In such an embodiment, thekiosk 740 may be equipped with a PIV or CAC card reader, a camera, andbiometric sensors (not shown in FIG. 7), as needed, to perform theauthentication mechanisms. The authentication mechanisms may verify thatthe user of the mobile computing device 710 is permitted to possess thederived credentials, in addition to authenticating the user of themobile computing device 710. The certificate management system server728 may access the user's information in the directory service 726 toauthenticate the user and to verify the user's permissions. Theauthentication mechanisms described herein should be the sameauthentication mechanisms that may already in use by the enterprise toeffect authentication with PIV or CAC cards in their organization. Inother words, the user of the mobile computing device 710 may already befamiliar with the authentication mechanisms described in the presentenrollment methods and techniques.

After the user has been authenticated, the certificate management systemapplication 714 may request and receive at least one or more derivedcredentials from the certificate management system server 728. Thederived credentials may comprise enrollment credentials,Secure/Multipurpose Internet Mail Extensions (S/MIME) encryption andsigning certificates, other network credentials, encryptioncertificates, signing certificates, and the like. The certificatemanagement system application 714 may be configured to encrypt thereceived derived credentials using a very strong form of encryption suchas Advanced Encryption Standard (AES) 256-bit encryption or the like.The certificate management system application 714 may salt theencryption algorithm with the user password provided by the enrollmentapplication 712 when the certificate management system application 714was launched. Alternatively, the certificate management systemapplication 714 may be configured to prompt the user of the mobilecomputing device 710 for the user password. The user password may bevalidated by the certificate management system application 714 with thepassword validation value retrieved from the shared vault 716. If orwhen the user password passes validation, the certificate managementsystem application 714 may store the encrypted derived credentials inthe shared vault 716 on the mobile computing device 710. In otherembodiments, the certificate management system application 714 mayencrypt the derived credentials using a private/public key pair, priorto storing the derived credentials in the shared vault 716 on the mobilecomputing device 710.

In some embodiments, the certificate management system application 714may authenticate to the certificate management system server 728 andstore the derived credentials in the shared vault 716 prior to startingthe present enrollment methods and techniques. In such an embodiment,the user of the mobile computing device 710 may complete theauthentication mechanisms described above and cause the certificatemanagement system application 714 to store the derived credentials inthe shared vault 716 prior to launching the enrollment application 712.

After the certificate management system application 714 has stored thederived credentials in the shared vault 716, the certificate managementsystem application 714 may cause the mobile computing device 710 toswitch control back to the enrollment application 712. The enrollmentapplication 712 may be configured to send a message to the enterprisemobile device management server 724 requesting the type of derivedcredentials needed to complete enrollment. In response to the request,the enterprise mobile device management server 724 may be configured tosend a message comprising information on the type of derived credentialsneeded to complete enrollment. The enrollment application 712 may beconfigured to retrieve a link to the derived credentials from the sharedvault 716. The enrollment application 712 may use the user passwordprovided by the user of the mobile computing device 710 to decrypt theencrypted derived credentials from the shared vault 716. Alternatively,the enrollment application 712 may prompt the user of the mobilecomputing device 710 for the user password if or when the enrollmentapplication 712 does not have the user password. For example, theenrollment application 712 may no longer have the user password becausethe user of the mobile computing device 710 may have inadvertentlystopped and restarted the enrollment application 712. The enrollmentapplication 712 may be configured to present the derived credentials tothe enterprise mobile device management server 724. The enterprisemobile device management server 724 may be configured to validate thederived credentials. The enterprise mobile device management server 724may communicate with the certificate management system server 728 toverify the validity of the derived credentials for the mobile computingdevice 710. The enterprise mobile device management server 724 may alsocommunicate with the directory service 726 to verify the validity of theuser of the mobile computing device 710. In some embodiments, theenrollment flow may require that the enrollment application 712 provideadditional derived credentials to the enterprise mobile devicemanagement server 724. In such embodiments, the enrollment application712 may retrieve and decrypt additional derived credentials from theshared vault 716 and provide the additional derived credentials to theenterprise mobile device management server 724. For example, theenterprise mobile device management server 724 may require one set ofderived credentials to complete mobile device management enrollment andmay require a different set of derived credentials to complete mobileapplication management enrollment. In other embodiments, the enterprisemobile device management server 724 may extract the username from thederived credentials provided by the enrollment application 712 ratherthan requesting the username from the enrollment application 712.

Once validation of the derived credentials is completed, the enrollmentflow may complete without the need for the user of the mobile computingdevice 710 to provide any further credentials. The enrollmentapplication 712 may access and configure the natively supported mobiledevice management (MDM) agent by the operating system of the mobilecomputing device 710. For example, on an iOS-based mobile computingdevice, the enrollment application 712 may configure the native MDMagent included with the iOS operating system. The enterprise mobiledevice management server 724 may also push policies to manage the mobilecomputing device 710 that are installed by the enrollment application712, as determined by the enterprise. The policies may be mobile devicemanagement policies, mobile application management policies, mobile datamanagement policies, or some combination of mobile device, application,and data management policies. The enterprise mobile device managementserver 724 may also push applications to be installed on the mobilecomputing device 710 by the enrollment application 712. As describedabove, in reference to FIG. 5, these applications may be secure, orcontainerized, applications or may be unsecure, or unmanaged,applications. Once the enrollment flow has completed, the mobilecomputing device 710 may be referred to as an enrolled device.

Advantageously, and as illustrated in greater detail above, anenterprise user might not have to know or enter their network ordirectory service password to enroll their mobile computing device withthe enterprise mobile device management server. In addition, theenrollment user experience is enhanced because a PIV or CAC card neednot be physically connected to the mobile computing device duringenrollment. Furthermore, the enterprise may manage the security of theenterprise resources accessed by the mobile computing device via theenterprise mobile device, application, and data management policiesprovisioned on the mobile computing device.

FIG. 7 illustrates just one example of a system architecture that may beused, and those of skill in the art will appreciate that the specificsystem architecture and computing devices used may vary, and aresecondary to the functionality that they provide, as further describedherein. For example, services provided by the automatic discovery server722 and the enterprise mobile device management server 724 may becombined on a single server or may be load balanced across a pluralityof servers.

FIGS. 8A-8C depict an example event sequence that illustrates a methodof enrolling a mobile computing device with an enterprise mobile devicemanagement service using derived credentials. As seen in FIGS. 8A-8C,one or more steps of the depicted example event sequence and othersimilar examples described herein may be performed in a computingenvironment such as the system illustrated in FIG. 7, as well as othersystems having different architectures (e.g., all or part of FIGS. 1-6).In other embodiments, the method illustrated in FIGS. 8A-8C and/or oneor more steps thereof may be embodied in a computer-readable medium,such as a non-transitory computer readable memory.

Referring to FIG. 8A, step 801, the enrollment application 712 mayprompt the user of the mobile computing device 710 for a username. Theenrollment application 712 may also prompt the user for the networkaddress to the enterprise mobile device management server 724. At step802, the enrollment application 712 may send a message to the automaticdiscovery server 722 requesting the configuration information for theenterprise mobile device management server 724. At step 803, theautomatic discovery server 722 may determine a response to the requestbased on the username and/or network address to the enterprise mobiledevice management server 724 provided by the enrollment application 712.At step 804, the enrollment application 712 may receive the response tothe configuration information request message from the automaticdiscovery server 722 comprising configuration information for theenterprise mobile device management server 724. At step 805, theenrollment application 712 may send an enrollment request message to theenterprise mobile device management server 724. The enrollment requestmessage may comprise the configuration information received from theautomatic discovery server 722. At step 806, the enrollment application712 may receive the response to the enrollment request message from theenterprise mobile device management server 724. The response from theenterprise mobile device management server 724 may comprise derivedcredential information, certificate management system applicationinformation, and password complexity rule information. At step 807, theenrollment application 712 may prompt the user for a password. Theenrollment application 712 may validate the user password using thepassword complexity rule information comprised in the enrollment requestresponse message received from the enterprise mobile device managementserver 724. If or when, the user password passes validation, theenrollment application 712 may generate a password validation valuebased on the user password and store the password validation value inthe shared vault 716, as shown in step 808. At step 809, the enrollmentapplication 712 may cause the mobile computing device 710 to switchcontrol over to the certificate management system application 714. Theenrollment application 712 may identify the certificate managementsystem application 714 to launch based on the certificate managementsystem application information comprised in the enrollment requestresponse message received from the enterprise mobile device managementserver 724. The enrollment application 712 may also provide the userpassword to the certificate management system application 714 at step809.

Referring to FIG. 8B, step 810, the certificate management systemapplication 714 may authenticate the user of the mobile computing deviceand the mobile computing device with the certificate management systemserver 728. As part of the authentication step 810, the certificatemanagement system server 728 may access the user's information in thedirectory service 726 to authenticate the user and to verify the user'spermissions as shown in step 810 a. At step 810 b, the certificatemanagement system server 728 may also obtain authentication informationfor the user from a PIV or CAC card and biometric sensors located at akiosk 740. The authentication mechanism described in step 810 may be themechanism determined by the enterprise to authenticate enterprise users.At step 811, the certificate management system application 714 may senda message to the certificate management system server 728 requestingderived credentials. At step 812, the certificate management systemserver 728 may respond to the request providing derived credentialswhich are then received by the certificate management system application714. If or when the certificate management system application 714 doesnot have the user password, the certificate management systemapplication 714 may prompt the user for the user password, as shown instep 813. At step 814, the certificate management system application 714may retrieve the password validation value from the shared vault 716 anddetermine the validity of the user password, as show in step 815. Atstep 816, the certificate management system application 714 may encryptthe derived credentials using the validated user password and store theencrypted derived credentials in the shared vault 716 as shown in step817. At step 818, the certificate management system application 714 maycause the mobile computing device to switch control back to theenrollment application 712.

Referring to FIG. 8C, step 819, the enrollment application 712 mayrequest the type of derived credentials needed to complete enrollmentfrom the enterprise mobile device management server 724. At step 820,the enterprise mobile device management server 724 may respond to therequest providing the type of derived credentials needed to completeenrollment. If or when, the enrollment application 712 does not have theuser password, then the enrollment application 712 may prompt the userof the mobile computing device 710 for the user password and validatethe user password using the password validation value retrieved from theshared vault 716, as shown in step 821. At step 822, the enrollmentapplication 712 may retrieve a link to the derived credentials from theshared vault 716. At step 823, the enrollment application 712 maypresent the derived credentials to the enterprise mobile devicemanagement server 724. At step 824, the enterprise mobile devicemanagement server 724 may validate the derived credentials presented bythe enrollment application 712. As part of the validation step 824, theenterprise mobile device management server 724 may communicate with thedirectory service 726 to verify the validity of the user of the mobilecomputing device 710, as shown in step 824 a. In step 824 b, theenterprise mobile device management server 724 may communicate with thecertificate management system server 728 to verify the validity of thederived credentials for the mobile computing device 710. At step 825,the enrollment flow may complete without the need for the user of themobile computing device 710 to provide any further credentials. Theenrollment application 712 may configure mobile device management (MDM)agent native to the operating system of the mobile computing device 710.The enterprise mobile device management server 724 may also pushpolicies to manage the mobile computing device 710 and installapplications on the mobile computing device 710. At step 826, the mobilecomputing device 710 may be referred to as an enrolled device.

FIG. 9 depicts an illustrative system architecture in which an enrolledmobile computing device 910 may use derived credentials in order toaccess enterprise resources 720. The architecture of the system depictedin FIG. 9 is similar in many respects to the architecture of the systemsdescribed above with reference to FIGS. 5, 6, and 7, and may includeadditional features not mentioned above. Some of the components of themobility management systems described above with reference to FIGS. 5,6, and 7 have been omitted for the sake of simplicity.

The enrolled mobile computing device 910 may be managed through theapplication of mobile device management policies as described above withreference to FIGS. 7 and 8A-8C. The containerized application 918 may bea secured, or managed, application as described above with reference toFIG. 5. Thus, the containerized application 918 may be subject to themobile device management policies enforced by the enrolled mobilecomputing device 910. The containerized application 918 may be an emailapplication, a web browsing application, a software-as-a-service (SaaS)application, an access application, and the like. The containerizedapplication 918 may be digitally signed with the same developmentsigning certificate as the enrollment application 712 and thecertificate management system application 714. Thus, the containerizedapplication 918 may access the password validation value stored in theshared vault 716 by the enrollment application 712 and the derivedcredentials stored in the shared vault 716 by the certificate managementsystem application 714, as described above with reference to FIGS. 7 and8A-8C. The containerized application 918 may be configured to prompt theuser of the enrolled mobile computing device 910 for the user password.The containerized application 918 may validate the user password usingthe password validation value retrieved from the shared vault 716. If orwhen the user password passes validation, the containerized application918 may retrieve a link to the derived credentials stored in the sharedvault 716. The containerized application 918 may access the enterpriseresources 720 directly or through the gateway 950.

The gateway 950 may be a single-server or multi-server system, or acloud-based system, including at least one virtualization server, asdescribed above with reference to FIG. 4. The containerized application918 may access the gateway 950 via a network 730. The gateway 950 mayinclude performance enhancement features that manage, accelerate, andimprove the delivery of enterprise resources 720 to the enrolled mobilecomputing device 910. An example of such a gateway is the NETSCALERGATEWAY manufactured by Citrix Systems, Inc., of Fort Lauderdale, Fla.The gateway 950 may be configured to require authentication credentialsin order to establish a communication connection with the enrolledmobile computing device 910. The containerized application 918 may beconfigured to retrieve a link to the necessary derived credentials fromthe shared vault 716 and provide them to the gateway 950 in order toestablish a connection to the gateway 950. The gateway 950 may beconfigured to access the user's information in the directory service 726to authenticate the user and to verify the user's permissions. Thegateway 950 may be further configured to communicate with thecertificate management system server 728 to verify the validity of thederived credentials for the enrolled mobile computing device 910. If orwhen the provided derived credentials are validated by the gateway 950and the communication connection is established, the containerizedapplication 918 may access enterprise resources 720 via the gateway 950.

The enterprise resources 720 may include email servers, file sharingservers, software-as-a-service (SaaS) application servers, webapplication servers, access application servers, and the like. Theenterprise server 960 may be a single-server or multi-server system, ora cloud-based system, including at least one virtualization server, asdescribed above with reference to FIG. 4. The containerized application918 may access the enterprise server 960 via a network 730 eitherdirectly or via the gateway 950. The enterprise server 960 may beconfigured to require authentication credentials in order for thecontainerized application 918 to establish a connection to theenterprise server 960. The enterprise server 960 may be furtherconfigured to require additional credentials, signing certificates,encryption certificates, and the like in order to provide resources andfunctionality to the containerized application 918. The containerizedapplication 918 may be configured to retrieve the necessary derivedcredentials from the shared vault 716 and present them to the enterpriseserver 960 as required to access the server resources and provide thenecessary functionality. For example, the containerized application 918may be a secure email application and the enterprise server 960 may be asecure email server. In such a scenario, the secure email server mayrequire authentication credentials in order to authenticate the user ofthe enrolled mobile computing device 910. The secure email applicationmay also require a signing certificate to digitally sign emails sent tothe secure email server for delivery and/or require encryptioncertificates to encrypt outgoing emails and decrypt incoming emails.Similarly to the gateway 950, the enterprise server may communicate withthe directory service 726 and the certificate management system server728 to authenticate the user of the enrolled mobile computing device 910and to validate the derived credentials provided by the containerizedapplication 918.

Advantageously, the approach implemented by the present methods andtechniques allows an enterprise user to access enterprise resources fromtheir enrolled mobile computing device without the need for theenterprise user to know or enter their network or directory servicepassword. In addition, the PIV or CAC card need not be physicallyconnected to the mobile computing device to obtain access. Furthermore,the mobile computing device is enrolled with the enterprise mobiledevice management server, thus allowing the enterprise to manage (e.g.,via the enterprise mobile device management server) the security of theenterprise resources accessed by the mobile computing device using oneor more enterprise mobile device policies, one or more applicationpolicies, and/or one or more data management policies defined by theenterprise.

FIG. 9 illustrates one example of a system architecture that may beused, and those of skill in the art will appreciate that the specificsystem architecture and computing devices used may vary, and aresecondary to the functionality that they provide, as further describedherein.

FIG. 10 depicts an example event sequence for providing a method for acontainerized application 918 to provide derived credentials stored in ashared vault 716 to an enterprise server 960. As seen in FIG. 10, one ormore steps of the depicted example event sequence and other similarexamples described herein may be performed in a computing environmentsuch as the system illustrated in FIG. 9, in addition to using othersystems having different architectures (e.g., all or part of FIGS. 1-7).In other embodiments, the method illustrated in FIG. 10 and/or one ormore steps thereof may be embodied in a computer-readable medium, suchas a non-transitory computer readable memory.

In further reference to FIG. 10, at step 1001, the containerizedapplication 918 may prompt the user of the mobile computing device 710for a user password. At step 1002, the containerized application 918 mayretrieve the password validation value from the shared vault 716 anddetermine the validity of the user password, as shown in step 1003. Atstep 1004, the containerized application 918 may retrieve a link to thederived credential from the shared vault 716. The containerizedapplication 918 may also decrypt the derived credential retrieved fromthe shared vault 716 using the validated user password. At step 1005,the containerized application 918 may present the decrypted derivedcredential to the gateway 950 in order to authenticate and establish acommunication connection. At step 1006, the gateway 950 may validate thederived credential presented by the containerized application 918. Aspart of the validation step 1006, the gateway 950 may communicate withthe directory service 726 to verify the validity of the user of theenrolled mobile computing device 910, as shown in step 1006 a. In step1006 b, the gateway 950 may communicate with the certificate managementsystem server 728 to verify the validity of the derived credentials forthe enrolled mobile computing device 910.

Referring to FIG. 10, step 1007, the containerized application 918 mayretrieve a link to the derived credential from the shared vault 716required by the enterprise server 960 to authenticate with and accessthe functionality of the enterprise server 960. The containerizedapplication 918 may also decrypt the derived credential retrieved fromthe shared vault 716 using the validated user password. In step 1008,the containerized application 918 may authenticate and obtain access tothe enterprise server 960 by presenting the decrypted derived credentialto the enterprise server 960, as determined by the enterprise server960. In step 1009, the containerized application 918 may retrieveadditional derived credentials from the shared vault 716 and presentthem to the enterprise server 960 as required to access the serverresources and provide the necessary functionality. As part of step 1009,the enterprise server 960 may communicate with the directory service 726to verify the validity of the user of the enrolled mobile computingdevice 910, as shown in step 1009 a. In step 1009 b, the enterpriseserver 960 may communicate with the certificate management system server728 to verify the validity of the derived credentials for the enrolledmobile computing device 910. For example, the containerized application918 may be a secure email application and the enterprise server 960 maybe a secure email server. In such a scenario, the secure email servermay require authentication credentials in order to authenticate the userof the enrolled mobile computing device 910. Once authenticated, thesecure email application may require additional credentials, such as asigning certificate to digitally sign emails sent to the secure emailserver for delivery encryption certificates to encrypt outgoing emailsand decrypt incoming emails, and the like. As another example, thecontainerized application 918 may be a secure agent and the enterpriseserver 960 may be a secure customer relationship management server. Thesecure agent may present an initial set of derived credentials to thesecure customer relationship management server to effect initialauthentication and access. Thereafter, the secure customer relationshipmanagement server may request additional authentication credentials toprovide access to highly secure aspects of the customer relationshipmanagement application

FIG. 11 depicts an example method of using derived credentials forenrollment with enterprise mobile device management services accordingto one or more illustrative aspects described herein. Referring to FIG.11, at step 1105, a mobile computing device may receive a command toenroll with an enterprise mobile device management server. At step 1110,in response to receiving the command to enroll with the enterprisemobile device management server, the mobile computing device may launchan enrollment application. At step 1115, the mobile computing device maysend, using the enrollment application, an enrollment request message tothe enterprise mobile device management server. At step 1120, the mobilecomputing device may switch from the enrollment application to acertificate management system application on the mobile computingdevice. At step 1125, the mobile computing device may request, using thecertificate management system application, one or more derivedcredentials from a certificate management system server. At step 1130,the mobile computing device may store, using the certificate managementsystem application, the one or more derived credentials in a sharedvault on the mobile computing device. At step 1135, the mobile computingdevice may switch from the certificate management system application tothe enrollment application. At step 1140, the mobile computing devicemay retrieve, using the enrollment application, a derived credential ofthe one or more derived credentials stored in the shared vault on themobile computing device. At step 1145, the mobile computing device mayprovide, using the enrollment application, the derived credential of theone or more derived credentials retrieved using the enrollmentapplication to the enterprise mobile device management server to enrollthe mobile computing device with at least one mobile device managementservice provided by the enterprise mobile device management server.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are described asexample implementations of the following claims.

What is claimed is:
 1. A method comprising: receiving, by a mobilecomputing device, a command to enroll with an enterprise mobile devicemanagement server; in response to receiving the command to enroll withthe enterprise mobile device management server, launching, by the mobilecomputing device, an enrollment application; requesting, by the mobilecomputing device, using the enrollment application, configurationinformation for the enterprise mobile device management server from anautomatic discovery service; after requesting the configurationinformation for the enterprise mobile device management server from theautomatic discovery service, receiving, by the mobile computing device,a message comprising the configuration information for the enterprisemobile device management server from the automatic discovery service;sending, by the mobile computing device, using the enrollmentapplication, an enrollment request message to the enterprise mobiledevice management server, wherein the enrollment request messagecomprises the configuration information for the enterprise mobile devicemanagement server received from the automatic discovery service;switching, by the mobile computing device, from the enrollmentapplication to a certificate management system application on the mobilecomputing device; requesting, by the mobile computing device, using thecertificate management system application, one or more derivedcredentials from a certificate management system server; storing, by themobile computing device, using the certificate management systemapplication, the one or more derived credentials in a shared vault onthe mobile computing device; switching, by the mobile computing device,from the certificate management system application to the enrollmentapplication; retrieving, by the mobile computing device, using theenrollment application, a derived credential of the one or more derivedcredentials stored in the shared vault on the mobile computing device;and providing, by the mobile computing device, using the enrollmentapplication, the derived credential of the one or more derivedcredentials retrieved using the enrollment application to the enterprisemobile device management server to enroll the mobile computing devicewith at least one mobile device management service provided by theenterprise mobile device management server.
 2. The method of claim 1,further comprising: prompting, by the mobile computing device, using theenrollment application, a user of the mobile computing device, for anaddress of the enterprise mobile device management server.
 3. The methodof claim 1, further comprising: receiving, by the mobile computingdevice, using the enrollment application, a password from a user of themobile computing device; generating, by the mobile computing device,using the enrollment application, a password validation value based onthe password received from the user of the mobile computing device;storing, by the mobile computing device, using the enrollmentapplication, the password validation value in the shared vault on themobile computing device; providing, by the mobile computing device,using the enrollment application, the password received from the user ofthe mobile computing device to the certificate management systemapplication; and validating, by the mobile computing device, using thecertificate management system application, the provided password to thecertificate management system application based on the passwordvalidation value stored in the shared vault on the mobile computingdevice.
 4. The method of claim 3, further comprising: receiving, by themobile computing device, responsive to the enrollment request message, amessage from the enterprise mobile device management server comprisingpassword complexity validation rules; and validating, by the mobilecomputing device, the password using the password complexity validationrules.
 5. The method of claim 3, wherein the generating the passwordvalidation value comprises: generating a hash of the password; andencrypting the hash of the password.
 6. The method of claim 3, furthercomprising: encrypting, by the mobile computing device, using thecertificate management system application, the one or more derivedcredentials based on the password received from the user of the mobilecomputing device and provided to the certificate management systemapplication, prior to storing the one or more derived credentials in theshared vault on the mobile computing device.
 7. The method of claim 3,further comprising: encrypting, by the mobile computing device, usingthe certificate management system application, the one or more derivedcredentials using a private/public key pair, prior to storing the one ormore derived credentials in the shared vault on the mobile computingdevice.
 8. The method of claim 1, further comprising: prior to switchingto the certificate management system application on the mobile computingdevice, receiving, by the mobile computing device, responsive to theenrollment request message, a message from the enterprise mobile devicemanagement server identifying the certificate management systemapplication on the mobile computing device; and determining, by themobile computing device, to switch to the certificate management systemapplication on the mobile computing device based on the message receivedfrom the enterprise mobile device management server identifying thecertificate management system application on the mobile computingdevice.
 9. The method of claim 1, further comprising: storing, by themobile computing device, using the certificate management systemapplication, at least one derived credential of the one or more derivedcredentials after an enrollment process is completed.
 10. The method ofclaim 1, wherein the enrollment application and the certificatemanagement system application are digitally signed with an identicaldevelopment signing certificate.
 11. The method of claim 10, furthercomprising: retrieving, by the mobile computing device, using one ormore applications on the mobile computing device that are digitallysigned with the same development signing certificate as the enrollmentapplication and the certificate management system application, at leastone derived credential of the one or more derived credentials from theshared vault; and using, by the mobile computing device the at least onederived credential of the one or more derived credentials retrieved fromthe shared vault to provide functionality in the one or moreapplications on the mobile computing device or to access enterpriseresources with the one or more applications on the mobile computingdevice.
 12. The method of claim 1, further comprising: retrieving, bythe mobile computing device, using the enrollment application, a firstderived credential and a second derived credential from the sharedvault; providing, by the mobile computing device, using the enrollmentapplication, the first derived credential to the enterprise mobiledevice management server to complete mobile device managementenrollment; and providing, by the mobile computing device, using theenrollment application, the second derived credential to the enterprisemobile device management server to complete mobile applicationmanagement enrollment.
 13. The method of claim 1, wherein the mobilecomputing device is provisioned by the enterprise mobile devicemanagement server with policies and applications after an enrollmentprocess is completed.
 14. The method of claim 1, further comprising:prior to requesting the one or more derived credentials from thecertificate management system server: authenticating, by the mobilecomputing device, using the certificate management system application,with the certificate management system server using the certificatemanagement system application.
 15. The method of claim 14, whereinauthenticating with the certificate management system server comprisesprompting a user of the mobile computing device to provide data foridentification and authentication purposes.
 16. The method of claim 1,wherein switching to the certificate management system application onthe mobile computing device comprises: launching an application store onthe mobile computing device; and prompting a user of the mobilecomputing device to install the certificate management systemapplication, if or when the certificate management system application isnot installed on the mobile computing device.
 17. A system, comprising:at least one processor; and at least one memory storing computerexecutable instructions that, when executed by the at least oneprocessor, cause the system to: receive a command to enroll with anenterprise mobile device management server; in response to receiving thecommand to enroll with the enterprise mobile device management server,launch an enrollment application; request, using the enrollmentapplication, configuration information for the enterprise mobile devicemanagement server from an automatic discovery service; after requestingthe configuration information for the enterprise mobile devicemanagement server from the automatic discovery service, receiving amessage comprising the configuration information for the enterprisemobile device management server from the automatic discovery service;send, using the enrollment application, an enrollment request message tothe enterprise mobile device management server, wherein the enrollmentrequest message comprises the configuration information for theenterprise mobile device management server received from the automaticdiscovery service; switch from the enrollment application to acertificate management system application; request, using thecertificate management system application, one or more derivedcredentials from a certificate management system server; store, usingthe certificate management system application, the one or more derivedcredentials in a shared vault; switch from the certificate managementsystem application to the enrollment application; retrieve, using theenrollment application, a derived credential of the one or more derivedcredentials stored in the shared vault; and provide, using theenrollment application, the derived credential of the one or morederived credentials retrieved using the enrollment application to theenterprise mobile device management server to enroll with at least onemobile device management service provided by the enterprise mobiledevice management server.
 18. One or more non-transitorycomputer-readable medium storing computer-executable instructions that,when executed by a computer system comprising at least one processor,and least one memory, cause the computer system to perform a methodcomprising: receiving a command to enroll with an enterprise mobiledevice management server; in response to receiving the command to enrollwith the enterprise mobile device management server, launching anenrollment application; requesting, using the enrollment application,configuration information for the enterprise mobile device managementserver from an automatic discovery service; after requesting theconfiguration information for the enterprise mobile device managementserver from the automatic discovery service, receiving a messagecomprising the configuration information for the enterprise mobiledevice management server from the automatic discovery service; sending,using the enrollment application, an enrollment request message to theenterprise mobile device management server, wherein the enrollmentrequest message comprises the configuration information for theenterprise mobile device management server received from the automaticdiscovery service; switching from the enrollment application to acertificate management system application; requesting, using thecertificate management system application, one or more derivedcredentials from a certificate management system server; storing, usingthe certificate management system application, the one or more derivedcredentials in a shared vault; switching from the certificate managementsystem application to the enrollment application; retrieving, using theenrollment application, a derived credential of the one or more derivedcredentials stored in the shared vault; and providing, using theenrollment application, the derived credential of the one or morederived credentials retrieved using the enrollment application to theenterprise mobile device management server to enroll with at least onemobile device management service provided by the enterprise mobiledevice management server.